PD ROM 1/PD ROM Volume I - Macintosh Software from BMUG (1988).iso/Electronic Messages/USEnet Digests/USEnet Vol. 4/USEnet 4.53

Text File | 1988-06-15 | 30.7 KB | 821 lines | [TEXT/ttxt]

25-Apr-88 11:43:11-PDT,32182;000000000000
Return-Path: <[e-mail]>
Received: from RELAY.CS.NET by SUMEX-AIM.Stanford.EDU with TCP; Mon, 25 Apr 88 11:41:56 PDT
Received: from relay2.cs.net by RELAY.CS.NET id aa12455; 25 Apr 88 12:13 EDT
Received: from relay.cs.net by RELAY.CS.NET id aa05433; 25 Apr 88 11:51 EDT
Received: from sdr.slb.com by RELAY.CS.NET id aa05385; 25 Apr 88 11:37 EDT
Date: Mon, 25 Apr 88 11:03 EDT
From: Jeffrey Shulman <[e-mail]>
Subject: Usenet Mac Digest V4 #53
To: [e-mail], [e-mail]
X-VMS-To: in%"[e-mail]",in%"[e-mail]"

Date: Mon 25 Apr 88 11:03:07-GMT
From: Jeff Shulman <SHULMAN@SDR>
Subject: Usenet Mac Digest V4 #53
To: Usenet-List: ;
Message-ID: <577965788.0.SHULMAN@SDR>
Mail-System-Version: <VAX-MM(218)+TOPSLIB(129)@SDR>

Usenet Mac Digest     Friday, April 22, 1988         Volume 4 : Issue 53

Today's Topics:
     How to achieve some amount of execute only from Appleshare
     Mac as an answering machine??
     word 3.01 and Thunder
     MacMan and double-clicking
     Power from serial port
     Re: Managing laser output in a student
     SB-Prolog port for Mac?
     Re: Mac as an answering machine??
     Font/DA Juggler +
     MAC II ROM Upgrade
     Re: MacMan and double-clicking
     Re: MAC II ROM Upgrade
     Re: MacMan
     Networking a whole bunch of Macs really fast
     I fixed an unreadable floppy...now you can too !
     Re: Networking a whole bunch of Macs really fast
     Re: E-mail Mac/Mainframe
     More on MPW tool graphics
     Re: screen swapping
     Re: TWO Byte Characters, SysEnvirons --
     Re: Opening Working Directories
     Re: How do you count unused master pointers?
     Re: More on MPW tool graphics
     Pointer arithmetic in C w/ or w/o locked handles
     Re: custom MDEF vs. MenuKey

----------------------------------------------------------------------

From: [e-mail] (Mike Rutenberg)
Subject: How to achieve some amount of execute only from Appleshare
Date: 15 Apr 88 06:27:40 GMT
Organization: Reed College, Portland OR

There are several solutions to the Appleshare execution problem. They
aren't foolproof, but they might take care of 99 and 44/100 % of your
problems.

Solution 1: If your environment consists of mostly floppy based
machines, make the applications too large to fit on a floppy.  Add some
new resources (call them NOPs or even something inconspicuous) which is
large enough to make it larger than 800k.  It will no longer be finder
copyable to a private diskette.  Note that this will take up more disk
space on your server, but it will not interfere with any of the caches
since that large resource will never be loaded off the disk.

Solution 2: Make the support files finder invisible.  Applications will
still be able to find most of them, but the program as stolen will be
less useful.  It also reduces the desktop clutter for people who just
want to use the program!!!  Eg. You can make Microsoft Word's Help file,
Dictionary, and Hyphenation file invisible and everything will work just
fine.

Solution 3: Don't make the real application visible.  Make it, as is,
invisible as in the previous solution.  Make sure to do this at the top
level of the directory hierarchy - this ensures you won't have
frustrated people who double click on their document but it can't find
the application.  So you ask, how do I launch the real application?

Create a small application in the your most yummy compiled language. The
complete Lightspeed C code follows:

    main() {
        Lauch(0, "\pServerDisk:Microsoft Word");
        }

Note that you do not have to initialize anything - doing so will take
longer and will reduce any feedback the finder the finder provides to
the person waiting patiently at their Mac (such as the watch cursor).

Build this launcher application, giving it the same icon as your real
application, the same SIZE (this might help Multifinder), an FREF, a
BNDL and all those other good things.  Name it something similar to your
actual application.  If the actual application is called Microsoft Word,
call this one Microsoft Word 3.01.  Similar names means that no matter
how people start up the real application, the finder puts up a similar
name.

When somebody clicks on this launcher application, it will immediately
launch the invisible (but still quite there) real application.  If the
user clicks on one of their documents, the real application will be
directly launched, making the whole process even faster.

Suggestions, comments?

I'd be happy to construct this for anyone without the technical
resources to do it.  I offer quick professional consulting, although
most of this is pretty straight forward to do if you are comfortable
mucking with Mac files.

Mike Rutenberg [phone]
--
Mike Rutenberg    for fast, robust food and software      [phone]


------------------------------

From: [e-mail] (Joe Hellerstein)
Subject: Mac as an answering machine??
Date: 15 Apr 88 18:56:02 GMT
Organization: Harvard Univ. Science Center

This might seem a rather expensive way of answering the phone, but
shouldn't a Mac with a modem be able to act as an answering machine? Is
there any existing software that does this?

Thanks in advance.

Joe Hellerstein


------------------------------

From: [e-mail] (Dan Gordon)
Subject: word 3.01 and Thunder
Date: 15 Apr 88 17:23:14 GMT
Organization: Teknowledge, Inc., Palo Alto CA

I use Thunder to do word counts on my Word 3.01 documents.  I select the
whole document, fire up thunder, ask to check the selection, and then
just execute STATS from the dialog box that ensues.

The problem is, Thunder gives me a different word count practically
every time I run this sequence.  The character count stays the same, but
the word count varies by +-20%.

Anyone have a clue what's happening?  How to fix?  Another way to get a
reasonably quick word count on a Word 3.01 document (the method of
copying the document and replacing all white space with \n and then
doing a line count which has been discussed here in the past is not
"reasonably quick", in my book)?

Thanks for any help,

Dan Gordon


------------------------------

From: [e-mail] (Wayne Mesard)
Subject: MacMan and double-clicking
Date: 15 Apr 88 21:20:36 GMT
Organization: Bolt Beranek and Newman Inc., Cambridge MA

A couple of people have posted saying that after running the MacMan
application, double clicking in the Finder no longer opens things (until
the machine is rebooted).

Is there anyone that this _doesn't_ happen to?  It sure is bugging the
heck out of me and my Mac+ running Finder 6.0/System 4.2.

I ran into a similar problem last year on someone else's machine.
(Double-clicking wouldn't work until AFTER an application had been run.)

Does anyone understand what's going on here, and more importantly, how
MacMan can be fixed?  (Is its author listening?)

--
unsigned *Wayne_Mesard();                     [e-mail]
                                              BBN Labs, Cambridge, MA
"All systems of useful complexity contain
 software errors."
               -The Eastport Report, p.14


------------------------------

From: [e-mail] (Ralph Martin)
Subject: Power from serial port
Date: 13 Apr 88 10:38:59 GMT
Organization: Univ. Coll. Cardiff, Cardiff, WALES, UK.

Old Macs used to have a +5v power pin on the serial ports. Alas, newer
ones dont, and I want to connect summat to the serial port which needs a
5v power supply at, say 20mA. It has been suggested to me that I can
just connect to the Handshake out Pin, and use that for my +5v. This
sounds too good to be true yet I suspect some such trick must work.

Anyone out there like to comment on this? Thanks, Ralph


------------------------------

From: [e-mail]
Subject: Re: Managing laser output in a student
Date: 14 Apr 88 16:15:00 GMT


[e-mail](John O'Malley) writes in comp.sys.mac

>We're in the early planning stages of setting up an open-access Macintosh
>lab for the Purdue campus.  We'll have lotsa networked Macs and probably a
>couple of LaserWriters.  We might charge for laser printouts.
>
>We'd like to figure out a way that we could automate the process of charging
>for the laser output.  One way would be to hook up a card reading device,
>similar to the copy-card readers (those credit-card like cards) that are
>often attached to photocopiers in campus libraries.  Has anyone had experience
>with this kind of thing?  Is it possible?  If such a device exists, I
>imagine that it'd have to be installed on a non-shared LaserWriter.

    Here at the University of Illinois, that is exactly what we do.  We
have attached a card reader to each of the public access LaserWriters
which is then attached to its own Macintosh (trying to handle the card
reader through a  shared (networked) system DOES NOT WORK TOO WELL
(causes a LOT of hassles)).
    We have found student fairly receptive to this method, the only problem
that we have encountered is that we only have a limited number of LW's
and lots of students.....
--
+---------------------------------+-----------------------------------+
+                                 +  Any thing I say may be taken as  +
+   Leonard Rosenthol             +  fact, then again you might decide+
+   President, LazerWare, inc.    +  that it really isn't, so you     +
+                                 +  never know, do you??             +
+   [e-mail]     +                                   +
+   GEnie:  MACgician             +                                   +
+   Delphi: MACgician             +                                   +
+                                 +                                   +
+---------------------------------+-----------------------------------+


------------------------------

From: [e-mail] (Eric Bowles)
Subject: SB-Prolog port for Mac?
Date: 16 Apr 88 02:35:48 GMT
Organization: University of California, Berkeley


Has anybody done a port of SB-Prolog for the Macintosh SE?  If so, how
can I get a copy of it?

I'd appreciate any information relating to the above. Thanks in advance.
--
================================================================================
Eric Bowles                                                       "Piyo Piyo"
ARPA:     [e-mail]
UUCP:     {decvax|hplabs|allegra|ihnp4|cbosgd}!ucbvax!ucbcory!bowles


------------------------------

From: [e-mail] (Barry Margolin)
Subject: Re: Mac as an answering machine??
Date: 16 Apr 88 07:19:03 GMT
Organization: Thinking Machines Corporation, Cambridge, MA

In article <[e-mail]> [e-mail] (Joe
Hellerstein) writes:
>but shouldn't a Mac with a modem be able to act as an answering machine?

You'll need more than a modem in order to do this.  The only sounds that
a modem knows how to make are the hisses that are used for data
transmission.  And the modem can only recognize the sounds that another
modem makes.  The interface that is used between the modem and the
computer does not permit full control of the sounds that are
transmitted.
--
Barry Margolin
Thinking Machines Corp.

[e-mail]
uunet!think!barmar


------------------------------

From: [e-mail] (Michael McDaniel)
Subject: Font/DA Juggler +
Date: 15 Apr 88 19:50:58 GMT
Organization: Dartmouth College, Hanover, NH

Configuration:  Mac SE/HD-20 Hard Disk/Font-DA Juggler +

If I shutdown without closing EVERY window on the screen, then Font/DA
Juggler + doesn't load at the start of the next session. Anyone have any
ideas/hints for how to fix this (other than closing all windows before
shutdow)?

Many Thanks in advance.  Please e-mail to me at the address below.
--
| Michael McDaniel                                                       |
| Usenet (UUCP):       ...!{harvard,linus,inhp4}!dartvax!u2!mdm          |
| Internet/BITNET:     [e-mail]                              |
| Spock:  I was attempting the hell to communicate.                      |


------------------------------

From: [e-mail] (Laurian Chirica)
Subject: MAC II ROM Upgrade
Date: 16 Apr 88 07:49:07 GMT
Organization: Cal Poly State Univ,CSC Dept,San Luis Obispo,CA 93407

Quote from Info World, April 11, 1988:

"Mac II users looking for more fire-power might ask their dealers for
the free ROM upgrade required to run A/UX.  I am not saying to pay the
$4,000 or so to actually buy A/UX; just get the ROM upgrade. It is free,
it gets you a brand-new mother board, and makes disk accesses under
Finder twice as fast.  No wonder Apple has been so quiet about this
freebie."

Question:  Does anyone know anything more about this?  My dealer knows
nothing.

--
Laurian M. Chirica  ([e-mail])
Computer Science Department
California Polytechnic State University (CAL POLY)
San Luis Obispo, CA 93407 - [phone]


------------------------------

From: [e-mail] (Mark E. Perkins)
Subject: Re: MacMan and double-clicking
Date: 16 Apr 88 14:34:00 GMT
Organization: New York University

> A couple of people have posted saying that after running the MacMan
> application, double clicking in the Finder no longer opens things (until
> the machine is rebooted).

    I notified the author about this problem not long after the posting.
I have not received any reply.

    The probelm is that MacMan (and some other stuff I've seen) is
leaving the System Event Mask set so that it ignores mouseUp events. The
Finder does not reset the mask to everyEvent.  Hence, the problem with
double-clicks.

    I have not found a way to patch these prpgrams directly, but I made
an FKEY that fixes the situation.  All it does is set the System Event
Mask to everyEvent, then return.  I can e-mail to anyone interested.  If
there is sufficient interest, I could post it (it's VERY short).

    Please direct responses to the address below.

    Mark Perkins
--
Internet:  [e-mail]    (that's VEE-EM-ELL)
Usenet:    {seismo|ihnp4|allegra}!cmcl2!vml!mark
US Mail:   Department of Psychology, NYU
       6 Washington Place, room 970
       New York, NY 10003
Phone:       [phone]


------------------------------

From: [e-mail] (Mark H. Anbinder)
Subject: Re: MAC II ROM Upgrade
Date: 16 Apr 88 17:46:31 GMT
Organization: Cornell Theory Center, Cornell University, Ithaca NY

The ROM upgrade has not yet shipped to dealers.  Keep asking your dealer
about it, though, as it's NOT likely to be announced to the general
public when it does ship.
--
Mark H. Anbinder, Cornell University Department of Media Services
[e-mail]
NG33 MVR Hall, Cornell Univ.
Ithaca, NY 14853        [phone]


------------------------------

From: [e-mail] (Jim Meiss)
Subject: Re: MacMan
Date: 16 Apr 88 20:01:11 GMT
Organization: UTexas Computation Center, Austin, Texas


    Instead of trying to use MacMan, with all its problems, I suggest
getting the "Inside Mac" DA from SUMEX. Its written by Bernard Gallet,
and puts up a window with two scrolling lists, one for the various
managers, and the other for each routine. Double clicking on the routine
puts its description in an edit box at the top of the window.
    This is a much nicer interface than macman's. It reads the same manual
as macman.

    This brings me to the question: has anybody seen IM vol IV and V in
this format?


                Jim Meiss
                 [e-mail]
                [e-mail]


------------------------------

From: [e-mail] (Mark McWiggins)
Subject: Networking a whole bunch of Macs really fast
Date: 15 Apr 88 21:57:42 GMT
Organization: Intek, Inc., Bellevue WA

We're about to bid on a project that requires the networking of 140+ Mac
SE's, using something faster than Appletalk.  What are our options? Our
network guy says that that's too many nodes for Ethernet (for this
amount of traffic, anyhow.)  Are there Arcnet (or other more
"egalitarian" network) implementations available for the Mac?  What
about TOPS?  Is it Ethernet-only, or are there other network options
available for it?

Any guidance would be most appreciated; thanks in advance.  Please send
E-mail, and I'll summarize for the net.
--

Mark McWiggins            UUCP:        uunet!intek01!mark
DISCLAIMER: I could be wrong.    INTERNET:    [e-mail]
                        [phone]


------------------------------

From: [e-mail]
Subject: I fixed an unreadable floppy...now you can too !
Date: 15 Apr 88 11:50:26 GMT

Ever had a disk go 'unreadable' on you ? Well, read on...

My MacWrite disk decided to self-destruct the other day...so badly that
the Finder kept saying that the 'disk is unreadable' !! Having plenty of
work on it, I set myself the task of fixing it.
   I first tried 'DiskExpress' which provides a Finder-like interface
for compressing/verifying/repairing disks. Unfortunately, it was TOO
much like the Finder - it claimed the disk was unreadable as well (with
a remarkably similar dialog box, I might add).
   Next, I tried 'Fedit+'. I really like this program - it's great for
just hacking around, so I was quite optimistic about my chances. At
least it recog- nised the faulty disk (it just called it 'External
Drive'), so I did an 'Open Volume' on it and -BINGO- up came sector 0 of
the disk. Simple investigation found that absolute sectors 3 and 4 were
unreadable, but Fedit+ wouldn't show me sectors 3 or 4 (it stuck on
sector 2 if I used Next Sector and sector 5 if I tried Prev Sector). So
I resorted to the good old 'Read Multiple Sectors' and 'Write Multiple
Sectors' with buffer 0, from sector 3 and length 2 sectors. I used 'Read
Mult...', ignored the error dialog, then 'Write Mult...'. Hooray ! I now
had readable sectors 3 and 4, but...they had rubbish in them.
   It now dawned on me that Fedit+ had no 'Repair boot tracks/directory
structure' option, but DiskExpress DID. So I trundled back to
DiskExpress, where I got 'Disk is damaged' instead. However, DiskExpress
bestowed pity on me and this time let me mount the disk and do things
with it. So I set the 'Repair Automatically' flag on and clicked on
'Start', then prayed...
   My prayers were answered. On exiting to the Finder, ejecting the
suspect disk (Shift-Command-2) and re-inserting it mounted a pefect
working copy of MacWrite. One disk backup later and I had a good disk
again.
   So the moral of this tail is - Don't Give Up (unless you're Kate Bush
or Peter Gabriel !) on bad disks : they can be salvaged with some
patience and copies of Fedit+ and DiskExpress.
--
Richard K. Lloyd,          ***************************************************
Computer Science Dept.,    * JANET : [e-mail]                   *
Liverpool University,      * UUCP  : {backbone}!mcvax!ukc!mupsy!liv-cs!SQRKL *
Merseyside, England,       * ARPA  : [e-mail]  *
Great (?) Britain.         ***************************************************

"I have VERY strong opinions which are nothing whatsoever to do with the
University of Liverpool, so blame ME if I bitch about useless IBM PC clones,
even more redundant IBM mainframes and the terrible Atari ST..."


------------------------------

From: [e-mail] (Bob Sutterfield)
Subject: Re: Networking a whole bunch of Macs really fast
Date: 17 Apr 88 17:39:06 GMT
Organization: The Ohio State University Dept of Computer & Information Science

Though that number of machines may overload a single Ethernet, why can't
you segregate them into smaller groups separated by routers or gateways?
 Your subnets may wind up matching the physical layout of the
installation anyway, which would make for easier installation and
troubleshooting. -=-
 Bob Sutterfield, Department of Computer and Information Science
 The Ohio State University; 2036 Neil Ave. Columbus OH USA 43210-1277
 [e-mail] or ...!att!osu-cis!bob


------------------------------

From: [e-mail] (Kevin M. Schofield)
Subject: Re: E-mail Mac/Mainframe
Date: 17 Apr 88 00:31:43 GMT
Organization: Dartmouth College, Hanover, NH

This appears to be a hot topic; it's been developing over the last few
months, and I would hazard a guess that it's going to get a lot hotter
in the next few months. Here at Dartmouth, we've looked at the email
products that currently exist for the Mac, and we're not happy with any
of them. We want a system that will handle 5000+ users, have an
interface to Internet-style mail, etc.  We've decided to write our own,
though I imagine that someone else will come along with one real soon.

There are lots of issues involved here:

   1. What mainframe to implement it on? (probably UNIX, but then we
still have
   the question of Appletalk support on a UNIX box).

   2. How many users will it support?

   3. What does the user interface look like? (believe me, this is NOT
an easy
   question, nor is there any obvious solution)

   4. What features should it support? filing of messages? enclosures?
   aliases/mailing lists? etc.

Ours is coming along nicely, but the server end is being written on a
mainframe running an operating system developed here at Dartmouth, and
so won't be portable.  I would be interested in hearing who else is
working on this, as I really do believe that a Mac email system with an
interface to mainframe mail will be in great demand in a few months.

-Kevin M. Schofield
 Software Development       Kiewit Computation Center  Dartmouth College


------------------------------

From: [e-mail] (Mike Blackwell)
Subject: More on MPW tool graphics
Date: 14 Apr 88 21:44:55 GMT
Organization: Carnegie-Mellon University, CS/RI

Okay, I can now open windows from a MPW tool, and draw in them. It works
okay - at least now I can see my data, but it's still pretty fragile,
and leaves a lot to be desired. Here are some of the problems I have:

Can't get events (update, in particular) from MPW, so I can't redraw the
window if it's been obscured, and then re-exposed.

If the graphic window is not the active window, then clicking on it will
make it active, as expected. The window can also be dragged. But, if the
window is active, and I click in the content region, MPW crashes doing a
GetPort.

There seems to be some problems using stdio to the Worksheet - sometimes
it takes a while for output to show up. Maybe just an occasional flush
in the tool will work - haven't tried that. Also, the cursor in the
Worksheet blinks very rapidly and erratically when the graphic window
exists.

I tried saving the current port, and only switching to the graphic port
when I was going to draw, and switching back when I was done, but that
caused things to crash...

If I command-. out of the tool, then the graphic window never gets
closed, and becomes unhooked from reality. No way to get rid of it, and
MPW isn't really happy...

Anyway, I've included the code fragments I've been using. If you have
any ideas on how to do things better, I'd really appreciate them!

        Mike Blackwell        [e-mail]

/* tool_graphics.c  --  Routines to manage a graphics window from an MPW
tool */

/* Mike Blackwell, Robotics Institute, Carnegie-Mellon University */

    #define __ALLNU__
    #include <Types.h>
    #include <Quickdraw.h>
    #include <Windows.h>

    extern struct qd qd;
    Rect graphicRect;
    WindowPtr graphicWindow;
    WindowRecord graphicWRecord;

    /* Open a graphic window with inside diminsions X by Y, centered */
    /* on the second graphic device screen if it exists, otherwise put it
*/
    /* on the main screen. The window is placed in the background. */
    open_graphic_window(X, Y, title)
    int X, Y;
    char *title;
    {
        GDHandle gdh;
        int top, left, height, width;

        InitGraf(&qd.thePort);
        gdh = GetMainDevice();
        if (GetNextDevice(gdh) != nil) gdh = GetNextDevice(gdh);
        height = (*gdh)->gdRect.bottom - (*gdh)->gdRect.top;
        width = (*gdh)->gdRect.right - (*gdh)->gdRect.left;
        top = (*gdh)->gdRect.top + (height - Y) / 2;
        left = (*gdh)->gdRect.left + (width - X) / 2;

        SetRect(&graphicRect, left, top, left + X, top + Y);
        graphicWindow = NewWindow(&graphicWRecord, &graphicRect, title,
                      true, 0, nil, false, nil);
        SetPort(graphicWindow);
    }


    /* This must be called before the program exits! */
    close_graphic_window()
    {
        CloseWindow(graphicWindow);
    }


------------------------------

From: [e-mail] (Jerry Whitnell)
Subject: Re: screen swapping
Date: 14 Apr 88 15:58:27 GMT
Organization: Communications Solutions Inc., San Jose, Ca

Beyond Dark Castle works on the Mac II in 2-bit mode (b&w).  Dark Castle
came out before the Mac II was known to exist and so does not work.  The
trick to supporting both seems simple enough with only a little extra
work on your part.  Detirmine whether you are running on a Plus/SE or a
II.  If on the Plus/SE, use screen swapping.  If on the II, make up a
offscreen bit-map that you draw into, then copybit the whole thing onto
the real screen.  On a II, in two-bit mode this should be fast enough. A
little more work and we II owners won't flame you when your program
doesn't work on our machines :-).
--
Jerry Whitnell                Been through Hell?
Communication Solutions, Inc.        What did you bring back for me?
                        - A. Brilliant


------------------------------

From: [e-mail] (Dan Allen)
Subject: Re: TWO Byte Characters, SysEnvirons --
Date: 15 Apr 88 05:45:51 GMT
Organization: Apple Computer Inc, Cupertino, CA

If the problem at hand is to simply write characters to a textfile with
MPW Pascal, and these characters are English (that is NOT Arabic,
Hebrew, Japanese, or Chinese), THEN your problem has absolutely nothing
to do with SysEnvirons, the Script Manager, or anything else that has to
do with Two Byte Characters, as that is all for international non-Roman
scripts.

What your problem DOES concern, is the fact that in MPW Pascal, a CHAR
occupies a word, which is TWO BYTES.  However, when writing CHARs to
textfiles, only a normal bytes worth is written, so your problem is
still a mystery.

Please send me more info and I'll see what I can do to help...
--
Dan Allen
MPW Engineer
Apple Computer


------------------------------

From: [e-mail] (Darin Adler)
Subject: Re: Opening Working Directories
Date: 15 Apr 88 07:35:07 GMT
Organization: Apple

In article <[e-mail]>
[e-mail] (Tom Carstensen) writes:
> I can't just go closing that last one I opened, it may
> have a file in it that I opened.

Once you have opened a file, the working directory no longer needs to be
open. HFS extracts the volume and directory information from the
WDRefNum when the Open call is made. You should always open working
directories for as short a time as possible, closing them after using
them. As a matter of fact, you can avoid opening working directories at
all by using the PBH calls, which take vRefNums and dirIDs to specify
the directory and volume a file is in.
--
Darin Adler, Apple Computer                          AppleLink:Adler4
UUCP: {sun,voder,nsc,mtxinu,dual}!apple!darin  CSNET: [e-mail]


------------------------------

From: [e-mail] (Darin Adler)
Subject: Re: How do you count unused master pointers?
Date: 15 Apr 88 07:38:29 GMT
Organization: Apple

In article <[e-mail]> [e-mail] (Scott Bayes)
writes:
> How likely is the master pointer format to change?

Master pointers will probably continue to work like they do today,
except that the additional information (locked, purgeable, and resource
bits) will be stored someplace other than the high byte of the master
pointer. One possiblity would be allocating a second long word, either
before or after the master pointer, and putting the bits there.
--
Darin Adler, Apple Computer                          AppleLink:Adler4
UUCP: {sun,voder,nsc,mtxinu,dual}!apple!darin  CSNET: [e-mail]


------------------------------

From: [e-mail] (Darin Adler)
Subject: Re: More on MPW tool graphics
Date: 15 Apr 88 21:48:29 GMT
Organization: Apple

In article <[e-mail]> [e-mail] (Mike Blackwell)
writes:
> If I command-. out of the tool, then the graphic window never gets closed,
> and becomes unhooked from reality. No way to get rid of it, and MPW isn't
> really happy...

You can use the MPW routine onexit (in StdLib.h) to add a routine to a
list of routines automatically called when the tool exits due to a
signal (such as the abort signal sent by Command-.).
--
Darin Adler, Apple Computer                          AppleLink:Adler4
UUCP: {sun,voder,nsc,mtxinu,dual}!apple!darin  CSNET: [e-mail]


------------------------------

From: [e-mail] (Tom Carstensen)
Subject: Pointer arithmetic in C w/ or w/o locked handles
Date: 15 Apr 88 19:53:34 GMT
Organization: Mentor Graphics Corporation, Beaverton Oregon

Is the problem I'm noticing with the following code fragment the
compiler, or on error:

    Handle hdl;
    char *ptr;
    long length;

    HLock(hdl);
    ptr = *hdl;

    while ( <condition> ) {
        /* ... stuff here ... */
        ptr++;
    }
    HUnlock(hdl);
    length = (long) (ptr - *hdl);

Running under The Debugger, I notice that the value for ptr = 80023678,
and the value for *hdl = 00023670, and therefore length becomes
80000008, which is actually a negative number.

The '8' (or 1000 binary) occurs because it is Locked -  (only on 68000
w/ 24 bit addressing).  but when I do pointer arithmetic, is the
compiler messing up or  should I only add Locked handles or Unlocked
handles together.

If I move the length calculation before I unlock the  handle, then
length becomes 8, and I'm ok.
--
:------------------------------------------------------------:
: Tom Carstensen         Usenet: [e-mail]      :
: Mentor Graphics                Delphi: CARSTENSEN          :
:                                GEnie:  XPC23637            :
:                                                            :
:     . . .  AAhh!  I see you have a machine that goes PING! :
:                                       - Monty Python       :
:------------------------------------------------------------:


------------------------------

From: [e-mail]
Subject: Re: custom MDEF vs. MenuKey
Date: 16 Apr 88 16:57:43 GMT

In article <[e-mail]>, [e-mail] (Brian H. Powell)
writes:
> the first few standard header bytes) from a regular MENU.
>      If you look at one of the custom MENUs with ResEdit, you get lots of
> gibberish.  In particular, the standard MENU template shows that an N
> appears in the MenuKey equivalent box.  Herein lies the problem.
>      We have a situation where NEW (normally cmd-N) is grayed out.
> Further down the menu bar is our custom menu.  MenuKey returns the custom
> menu's ID if NEW is grayed out.

Add a filler of two zero bytes after the standard components of the
record. This will stop MenuKey from interpreting the rest of the record.
It also stops ResEdit from displaying garbage, but it does not stop it
from truncating the menu :-(
--
Joachim Lindenberg, University of Karlsruhe
Federal Republic of Germany - West Germany.

------------------------------

End of Usenet Mac Digest
************************
-------